Method For Distribution of Software and Configuration Data and Corresponding Data Network

ABSTRACT

In one aspect, software or configuration data that is to be distributed is subdivided into data blocks and a list created based on the data blocks created. Users receive the list and a portion of the data blocks. The users form ad hoc networks or P2P connections among themselves. The connections allow the data blocks to be exchanged randomly.

The present invention relates to a method for distribution of software and/or configuration data in a data network with a number of users who have ad hoc-networking capabilities. In addition the present invention relates to a corresponding data network with users who have ad-hoc networking capabilities and a central device for distribution of the software or configuration data.

Software administration plays a central role for any mobile radio network provider or network operator. With several million users the providers or operators are confronted with an enormous problem: The changing and updating of configurations is to be able to be undertaken at all terminals simultaneously or within a time frame for which oversight is possible. While the standards bodies concentrate on how the updating and changing of the configurations is to be managed on the network side and on terminal side, the process to be employed by network providers and operators for handling the multiplicity of triggers and connections for updates and changes has basically been left open.

The object of the present invention is thus to provide a method with which an update or change of the configurations of a plurality of terminals can be undertaken more easily. In addition a corresponding data network is to be specified.

In accordance with the invention this object is achieved by a method of distributing software and/or configuration data in a data network with a number of users who have ad hoc-networking capabilities by dividing up the software and/or configuration data to be distributed into at least a first and a second data block, transmitting the first data block from a central location to a first of the number of users and the second data block likewise from a central location to a second of the number of users, establishing spontaneous communication between the first and second user and sending the second data block directly from the second user to the first user.

In addition there is provision according to the invention for a data network with at least one first and one second user who have ad hoc networking capabilities, and a central device for distributing software and/or configuration data, with the software and/or configuration data to be distributed being available in at least one first and one second data block, the first data block being able to be sent by the central device to the first user and the second data block to the second user, spontaneous communication being able to be established between the first and second user and the second data block being able to be sent directly from the second user to the first user.

Advantageously this makes it possible for the network providers and operators to no longer have to trigger all devices or users for updating and changing the configurations or software. They merely have to send software or configuration data to a subset of users. This saves energy and bandwidth and thereby money. Specifically, by dividing up the configuration data to be transmitted into data blocks, around one third of the distribution costs can be saved compared to a standard P2P (peer-to-peer) software distribution.

Preferably in the inventive method a list is created reflecting a complete set of data blocks which is produced during the division. This list is then sent together with a data block to the user concerned. Since a user does not receive from the central location the complete set of data blocks for the configuration, they are informed by the list about the data blocks which they must obtain from other users through spontaneous communication, i.e. by means of a P2P connection or ad-hoc network.

The second data block can be sent by the second user at the request of the first user. In this case the first user, who is still missing the second data block, is the active part. An especially efficient method of doing this is for the first user to make their request on the basis of the list, which they have obtained from the central location, to the user forming an ad-hoc network with them.

The second data block can however also be transmitted automatically by the second user, if they establish communication with the first user or set up the ad-hoc network. This means that in this case the second user is the active part and the first user merely has to decide whether they already have the second data block and discard it if necessary.

As soon as one of the number of users has a complete set of data blocks available, their installation or setup can be started. The user can establish on the basis of the list transferred by the central location whether the set of data blocks is complete or not.

Spontaneous communication can be established using Bluetooth or WLAN. This allows the process to be based on known standards.

The present invention will now be explained in greater detail with reference to the enclosed drawings, which basically reflect an inventive data network.

The exemplary embodiment described in greater detail below represents a preferred embodiment of the present invention.

The inventive solution is based on a P2P software management distribution principle with part delivery. In this case large volumes of data needed for the updating or changing of the software or configuration are divided up into blocks which are then sent to “selected” devices. To this end only one data block is sent to a device in each case.

In the example of FIG. 1 the operator 0 provides a data set D with which the users T1, T2 and T3 of a mobile radio network are to be newly configured. In this case the data of the data set D is subdivided into blocks A, B and C. Furthermore the data set D possesses a list L which contains a script about all the data blocks A, B and C to be received by the users.

Operator 0 now sends the individual data blocks A, B and C via send stations S1 and S2 to the users T1, T2 and T3. Data is also sent to user T5 from send station S1.

In the actual example the send station S1 sends a data block A including the list L to the user T1. Furthermore the send station S1 sends a data block B including list L to a user T2. The other send station S2 sends a data block C including list L to a user T3. The restriction to a few users and send stations is based on a purely arbitrary selection. Basically any number of send stations and users can be selected.

In addition the send station S1 also transmits to a user T5 the data block B including list L. Using spontaneous communication the user T1 also forwards the data block A with list L received from the send station S1 to user T4. In this way the data can not only be transported onwards via the send stations S1 and S2, but also, in a similar manner to the virus dissemination principle, between the users themselves.

Since the users who have received new data also received a list providing information about all the necessary data blocks, the users also know which data blocks they still do not have. In order however not to occupy the data network unnecessarily with the forwarding of configuration data, an additional dissemination mechanism is provided in accordance with the invention. If namely a user moves towards another user (in the example shown in the figure user T3 is moving towards user T2) the two users, if they are at an appropriate distance from each other, can establish an ad-hoc-network or a P2P connection via Bluetooth or WLAN. The configuration data blocks can then be exchanged via this communication connection. In the case shown here user T2 sends data block B to user T3 and user T3 sends data block C to user T2. This is done either by user T3 issuing data block C automatically if a P2P connection is established to another user. In the same way user T2 could automatically issue data block B if this P2P connection is established to another user.

Alternately each user can make use of the list L since they know from this list the data blocks which they do not yet have for a complete set of configuration data. In the present example this would mean user T2 asking user T3 whether they have data block A or C available. Since user T3 possesses data block C, they send data block C to user T2. The same applies to the transmission of data block B from user T2 to user T3. Finally the two users T2 and T3 each have the two data blocks B and C. It is then only necessary to wait until one of the two users T2 and T3 is in contact with user T1 or T4 for example, so that they can obtain the remaining data block A.

This viral dissemination of data blocks for configuration or other software updating means that less of a load is imposed on the data network, so that less bandwidth is necessary for software management. The transmission of the data blocks is guaranteed instead by ad-hoc connections between the terminals. This principle is of especial interest for large volumes of data to be distributed cost-effectively.

LIST OF REFERENCE SYMBOLS

-   A, B, C Data blocks -   D Data set -   L List -   O Operator -   P2P Peer-to-peer connection -   S1, S2 Send stations -   T1, T2, T3, T4, T5 Users 

1.-12. (canceled)
 13. A method for distributing data in a data network comprising a plurality of subscribers having ad hoc-networking capabilities, the method comprising: dividing the data to be distributed into a plurality of data blocks including a first and a second data block; creating a list reflecting a complete set of the data blocks produced during the division; sending the first data block and the list from a central location to a first subscriber; sending the second data block and the list the central location to a second subscriber; establishing spontaneous communication between the first and second subscriber; and sending the second data block and the list from the second subscriber to the first subscriber.
 14. The method as claimed in claim 13, wherein the second data block is sent in response to a request by the first subscriber.
 15. The method as claimed in claim 14, wherein the request is made based on the list.
 16. The method as claimed in claim 15, wherein the first subscriber determines from the list a data block not received by the first subscriber, and wherein the request includes information relating to the data block not received.
 17. The method as claimed in claim 13, wherein the second data block is sent automatically by the second subscriber after the communication establishment with the first subscriber.
 18. The method as claimed in claim 13, further comprising starting an installation or a setup when a subscriber from the plurality of subscribers has received a complete set of the data blocks.
 19. The method as claimed in claim 13, wherein the data is software data or a configuration data.
 20. The method as claimed in claim 13, wherein the spontaneous communication is set up using Bluetooth or WLAN.
 21. A data network, comprising: a central device for distributing data; a plurality of subscribers including a first subscriber and a second subscriber, the plurality of subscribers having network capabilities; a plurality of data blocks including a first data block and a second the data block, the data blocks formed from dividing the data; a list created in the central device reflecting a complete set of the data blocks produced during the division; and a communications path spontaneous established between the first and second subscribers; wherein the central device sends the first data block and the list to the first subscriber and sends the second data block and the list to the second subscriber, and wherein the second subscriber transmits the second data block and the list directly to the first subscriber via the communications path
 22. The data network as claimed in claim 21, wherein the data is software data or a configuration data.
 23. The data network as claimed in claim 22, wherein the transmission by the second subscriber is in response to a request by the first subscriber.
 24. The data network as claimed in claim 23, wherein the request is made based of the list.
 25. The data network as claimed in claim 24, wherein the first subscriber determines from the list a data block not received by the first subscriber, and wherein the request includes information relating to the data block not received.
 26. The data network as claimed in claim 22, wherein the second data block is transmitted automatically by the second subscriber to the first subscriber.
 27. The data network as claimed in claim 22, wherein an installation or a setup is started in a subscriber from the plurality of subscribers that has received a complete set of data blocks.
 28. The data network as claimed in claim 22, wherein with the spontaneous communication path between the subscribers is established using Bluetooth or WLAN. 